Hello!

Cross-posted per Mohan Suryanarayan's comment here.

This problem is similar to this problem. The exception is that instead of an explicitly permitted user receiving a "no connection" notification, a user that should fall under Default "Free/Busy" gets "no connection" on shared calendars. Here's some pertinent information:

• The user is on a personal, non-domain joined machine.
• The user is connecting via HTTP (with msstd defined for proxy connections) from Outlook to Exchange 2007.
• The user connects to shared calendars WITHOUT ERRORS when logging into the domain on a DJ'ed computer.
• Per the aforementioned article, adding him as an editor to the calendar allows him error-free connection.
  • Interestingly enough, removing that permission allows him to continue the connection for a time, but he still sees everything instead of reverting to default free/busy.

Here's what I've done so far:

• Added Editor rights manually to a shared calendar, which allowed connection, but then removed, which maintained connection and then removed it after about 15 mins.
• Toggled Cached mode, without success.
• Resynced his profile, without success.
• Removed and recreated his profile, without success.
• Turned on logging, which created ETL files in the OKCalLog directory in normal logging location (%temp% etc. etc.), but which ETLs yielded event codes for which Google had no useful input (and very little user friendly information besides). Codes 120 and 170 were most pertinent.

This user was previously working on domain-joined machines only. As I mentioned, when he logs in to a domain-joined machine, he has no issues.

Help! What am I missing?

The difference between connecting with a domain-joined machine versus a workgroup machine is that the domain-joined computer's Outlook gets Autodiscover from the SCP in Active Directory, whereas the workgroup machine looks to DNS (domain.com, Autodiscover.domain.com and then a SRV record).  If you're not properly publishing Exchange Web Services with an ExternalUrl, the workgroup client won't know where to go.

I will run this by the sysadmin and let you know if there's a URL problem. Thanks for the reply.

Big thanks, Ed. You got us on the right track. We had the DNS set up with the SRV and domain, but we didn't have an A record for Autodiscover. Adding that kicked it in gear and the calendars started syncing up just fine.